-
Notifications
You must be signed in to change notification settings - Fork 167
Combining multiple object files in JIT #2530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
mawad-amd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for writing this. This approach looks fine to me and tying the code object name to the kernel itself is good enough for me for now. The non-ideal thing here is that a user must have one function per source file. It's not ideal but a non-issue for me. I will let Jeff and Joe decide if that's an issue.
I ported the tests I wrote to have each function in different file here if you wanted to reuse them https://gist.github.com/mawad-amd/56fed24599343f22ab4f51d0c679a4a9
That is true, you can't have more than one function referenced from an ExternalFunction in a single compilation unit as the current ExternalFunction design has 1:1 map between external function and compilation units. This is only a prototype to allow the use-case that was brought up. I don't have a good solution for having multiple ExternalFunctions to bind to the same object file. Maybe we allow one ExternalFunction to bind to another one? Or create an array of ExternalFunctions? |
88a0a36 to
6924e03
Compare
6924e03 to
5dea96a
Compare
5dea96a to
3dcca27
Compare
3dcca27 to
cab831f
Compare
cab831f to
01e9e29
Compare
No description provided.